chore(release): sync open-scaffold@0.33.0 — evidence battery package sync - #228
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 1b3646ebaf
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
1b3646e to
c716052
Compare
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: c7160527ac
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
c716052 to
f392fa5
Compare
|
@codex review Please review PR #228 latest head f392fa5. Prior P2s (evidence note Summary claimed published; plan/evidence marked PR merge as passed before merge) are fixed: evidence note Summary is candidate wording, merge gates are unchecked in both the evidence note and plan, and CHANGELOG/evidence/plan are all candidate state until post-merge publication proof. Report any remaining actionable issues or confirm none. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: f392fa582f
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
f392fa5 to
6e24475
Compare
|
@codex review Please review PR #228 latest head 6e24475. Prior P2s fixed: (1) plan Context no longer says 'merge (already done)' — clarified PR #226 merged, this PR merges after review; (2) evidence note CI gate no longer pins the stale c716052 head; (3) docs/STABILITY.md, README.md, and ROADMAP.md forward-line references updated v0.32.x -> v0.33.x for the new minor line (matching the PR #216 pattern). Report any remaining actionable issues or confirm none. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 6e24475d4a
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
…sync Bump package version 0.32.1 -> 0.33.0 (package.json + package-lock.json root and packages[""] fields). Add v0.33.0 CHANGELOG entry (candidate state until trusted publishing completes) and keep v0.32.1 as current Latest. Add release-sync plan 174 (prep done; publication is owner-approved follow-through, not an AC) and candidate evidence note. Update section-parser live-corpus hashes for the new plan/evidence/changelog. Publishes the fail-closed evidence battery from PR #226 to the public npm and GitHub release surfaces via owner-approved trusted publishing.
6e24475 to
4f7ea49
Compare
|
@codex review Please review PR #228 latest head 4f7ea49. Prior P2 (plan in done/ with an unchecked merge AC) is fixed: the merge step was removed from the plan's acceptance criteria, so all plan 174 ACs are checked; merge/publish remain owner-approved follow-through recorded in the evidence note, not ACs. Report any remaining actionable issues or confirm none. |
Summary
Release-sync for
open-scaffold@0.33.0— publishes the fail-closed evidence battery from PR #226 to the public npm and GitHub release surfaces via owner-approved trusted publishing.PR #226 (squash-merged as
55644b8) addedevidence_batterysupport to proof manifests: a gate that blocksboundedProofwhen required evidence is notdemonstrated/reproduced,not_evaluatedreporting for empty batteries, a manifest-levelrequired_evidencelist (omission is a structural failure, membership implies required-for-pass, IDs trimmed in both paths), and a proof-battery table inosc prove compare. Codex reviewed the latest headf84a4343e4clean on 2026-06-20 with zero unresolved review threads;mainCI is green.Changes
package.json+package-lock.json— bump0.32.1→0.33.0(root andpackages[""]lockfile fields).docs/CHANGELOG.md— addv0.33.0entry; markv0.32.1superseded..osc/plans/done/174-evidence-battery-package-sync.md— release-sync plan..osc/releases/2026-06-20-174-evidence-battery-package-sync.md— candidate publication evidence note (final proof URLs recorded in release follow-through closeout after trusted publishing).tests/section-parser.test.ts— updated live-corpus hashes for the new plan/evidence/changelog.Pre-1.0 boundary
Minor release for a new proof-harness feature. The Codex 2x cold-resume claim remains bounded to its single fixture; human-reviewer replication and controlled ablations remain disclosure-only. This is not production-readiness, compliance certification, broad adoption proof, or mature 1.0 status.
Verification (local, candidate)
npm ci— PASS (0 vulnerabilities).git diff --check— PASS../verify.sh --strict— PASS: 10 pass / 0 fail / 0 warn (plan immutability intact; release-note structure valid).npm test -- --run— PASS: 48 files / 563 tests.npm run build— PASS.npm run osc -- doctor --check secret-scan— PASS.npm pack --dry-run --json— PASS:open-scaffold@0.33.0, 226 files,dist/cli.js+ README + docs present, no.pyc/__pycache__/raw.tsresidue.npm publish --dry-run --tag latest— PASS (dry-run only).Publication follow-through (after merge)
Owner-approved: trigger
publish-npm.ymlworkflow_dispatch (expected-version=0.33.0, taglatest), verifynpm view open-scaffold version→0.33.0, fresh isolated-cachenpx open-scaffold@latest --versionsmoke, and create GitHub Releasev0.33.0as Latest. A small follow-up PR records the final publish-proof URLs in the evidence note.No merge of this PR constitutes publication; trusted publishing is a separate, owner-approved step.